R4 Draft for Comment

This page is part of the FHIR Specification (v3.2.0: R4 Ballot 1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4 R3

4.3.2.18977 HL7 v3 Value Set ActRelationshipConditional

Vocabulary Work Group Maturity Level: N/AExternal Use Context: Any

This value set (http://hl7.org/fhir/ValueSet/v3-ActRelationshipConditional) is defined as part of HL7 v3. Related FHIR content: ActRelationshipConditional.

Summary

Defining URL:http://hl7.org/fhir/ValueSet/v3-ActRelationshipConditional
Name:ActRelationshipConditional
Definition:

Specifies under what circumstances (target Act) the source-Act may, must, must not or has occurred

OID:2.16.840.1.113883.1.11.18977 (for OID based terminology systems)
Source ResourceXML / JSON

This value set is not currently used

4.3.2.18977.1 Content Logical Definition

This value set includes codes from the following code systems:

 

4.3.2.18977.2 Expansion

This expansion generated 20 Dec 2017

This value set contains 17 concepts

Expansion based on http://hl7.org/fhir/v3/ActRelationshipType version 2017-07-31

All codes from system http://hl7.org/fhir/v3/ActRelationshipType

CodeDisplayDefinition
CINDhas contra-indicationA contraindication is just a negation of a reason, i.e. it gives a condition under which the action is not to be done. Both, source and target can be any kind of service; target service is in criterion mood. How the strength of a contraindication is expressed (e.g., relative, absolute) is left as an open issue. The priorityNumber attribute could be used.
PRCNhas pre-conditionA requirement to be true before a service is performed. The target can be any service in criterion mood. For multiple pre-conditions a conjunction attribute (AND, OR, XOR) is applicable.
RSONhas reasonDescription: The reason or rationale for a service. A reason link is weaker than a trigger, it only suggests that some service may be or might have been a reason for some action, but not that this reason requires/required the action to be taken. Also, as opposed to the trigger, there is no strong timely relation between the reason and the action. As well as providing various types of information about the rationale for a service, the RSON act relationship is routinely used between a SBADM act and an OBS act to describe the indication for use of a medication. Child concepts may be used to describe types of indication. Discussion: In prior releases, the code "SUGG" (suggests) was expressed as "an inversion of the reason link." That code has been retired in favor of the inversion indicator that is an attribute of ActRelationship.
BLOCKblocksDefinition: The source act is performed to block the effects of the target act. This act relationship should be used when describing near miss type incidents where potential harm could have occurred, but the action described in the source act blocked the potential harmful effects of the incident actually occurring.
DIAGdiagnosesDescription: The source act is intended to help establish the presence of a (an adverse) situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature.
IMMimmunization againstDescription: The source act is intented to provide immunity against the effects of the target act (the target act describes an infectious disease)
ACTIMMactive immunization againstDescription: The source act is intended to provide active immunity against the effects of the target act (the target act describes an infectious disease)
PASSIMMpassive immunization againstDescription: The source act is intended to provide passive immunity against the effects of the target act (the target act describes an infectious disease).
MITGTmitigatesThe source act removes or lessens the occurrence or effect of the target act.
RCVYrecoversDefinition: The source act is performed to recover from the effects of the target act.
PRYLXprophylaxis ofDescription: The source act is intended to reduce the risk of of an adverse situation to emerge as described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature.
TREATtreatsDescription: The source act is intended to improve a pre-existing adverse situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature.
ADJUNCTadjunctive treatmentDescription: The source act is intended to offer an additional treatment for the management or cure of a pre-existing adverse situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature. It is not a requirement that the non-adjunctive treatment is explicitly specified.
MTREATmaintenance treatmentDescription: The source act is intended to provide long term maintenance improvement or management of a pre-existing adverse situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature.
PALLTREATpalliatesDescription: The source act is intended to provide palliation for the effects of the target act.
SYMPsymptomatic reliefDescription: The source act is intented to provide symptomatic relief for the effects of the target act.
TRIGhas triggerA pre-condition that if true should result in the source Act being executed. The target is in typically in criterion mood. When reported after the fact (i.e. the criterion has been met) it may be in Event mood. A delay between the trigger and the triggered action can be specified. Discussion: This includes the concept of a required act for a service or financial instrument such as an insurance plan or policy. In such cases, the trigger is the occurrence of a specific condition such as coverage limits being exceeded.